Search Results

Tackling NVH one dB per day New tools and technologies are helping engineers reduce vehicle Noise, Vibration and Harshness. Artificial intelligence becomes a reality Automakers could be among the leaders in deploying AI in free-standing, high-reliability environments. But developers must determine how to mitigate undesirable side-effects. Lidar: autonomy's mission-critical component Automated-driving capability likely won't happen without Lidar. But what technology-and at what price? Formula One goes longer, lower, wider for 2017 New rules make the cars faster and more aggressive-looking, with a wider track, wider tires and bigger wings. Editorial: Core Ford, New Ford...OneFord? SAE Standards News Seeking a common language for vehicle automation Supplier Eye Are you innovating for NVH?

HMIs extend beyond the cab Telematics functions are being integrated into multi-function user interfaces. Standards step forward in design of off-highway electronics Functional safety standards are starting to impact many development projects, while the auto industry's AUTOSAR standard is being deployed to help enable software reuse and simplify designs. Leveraging automotive lightweighting techniques to improve off-highway emissions Where systems engineers can gain efficiencies in off-highway equipment is agnostic, they'll take it anywhere, and so they should, but one of the ways, often underestimated, is through the use of strong and lightweight advanced materials. Waste heat recovery for the long haul A WHR system based on an organic Rankine cycle has been developed for a long-haul Iveco Stralis truck.

In this paper, we outline past, present and future applications of automotive security for engine ECUs. Electronic immobilizers and anti-tuning countermeasures have been used for several years. Recently, OEMs and suppliers are facing more and more powerful attackers, and as a result, have introduced stronger countermeasures based on hardware security. Finally, with the advent of connected cars, it is expected that many things that currently require a physical connection will be done remotely in a near future. This includes remote diagnostics, reprogramming and engine calibration.

To serve and protect As cars become more connected and automated, cybersecurity concerns are rising. Industry engineers have many tools and techniques and are now deploying encryption and standards to ensure that vehicle controls are not altered or usurped by unauthorized people.

The federal government and industry have moved to concurrent acquisition and development processes using integrated process teams (IPTs). These processes are supported by timely, accurate, cross functional access to data within an integrated data environment (IDE) enabled by advances in information technology (IT). Since the advent of acquisition reform in 1994, Data Management (DM) practices have evolved from being directed by a prescriptive set of standards and procedures to use of the guidance in a principles-based standard -- ANSI/EIA 859.

GEIA Handbook 859 provides implementation guidance for ANSI/EIA 859, with discussions of applications of the standard's principles, tools, examples, and case studies. Handbook 859 is organized according to the lifecycle of data management and covers activities from the pre-RFP stage through records disposition.

This SAE Recommended Practice establishes a uniform practice for protecting vehicle components from "unauthorized" access through a vehicle data link connector (DLC). The document defines a security system for motor vehicle and tool manufacturers. It will provide flexibility to tailor systems to the security needs of the vehicle manufacturer. The vehicle modules addressed are those that are capable of having solid state memory contents accessed or altered through the data link connector. Improper memory content alteration could potentially damage the electronics or other vehicle modules; risk the vehicle compliance to government legislated requirements; or risk the vehicle manufacturer's security interests. This document does not imply that other security measures are not required nor possible.

This SAE Recommended Practice defines the Expanded Diagnostic Protocol (EDP), the requirements for the SAE J1978 OBD II Scan Tool for supporting the EDP protocol, and associated requirements for diagnosis and service information to be provided by motor vehicle manufacturers. Appendix A includes worked examples of the use of the protocol.

This SAE Recommended Practice defines the Expanded Diagnostic Protocol (EDP), the requirements for the SAE J1978 OBD II Scan Tool for supporting the EDP protocol, and associated requirements for diagnosis and service information to be provided by motor vehicle manufacturers. Appendix A includes worked examples of the use of the protocol.